Fix: Corrected grammar and typos in website content #1974
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@dineshgokaram is attempting to deploy a commit to the Piyush Garg's projects Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR fixes various grammatical and spelling errors across the website content, improving overall readability and professionalism.
Fixes #1972
Type of change
-Bug fix (non-breaking change that corrects text/content)
-Chore (minor content refinements or non-functional changes)
How should this be tested?
1.Run the app locally using npm run dev
2.Navigate through all affected pages
3.Verify that:
Grammar and spelling are correct
No layout or styling was unintentionally affected
Mandatory Tasks
I have reviewed all changes to ensure correctness
Verified the site renders correctly after updates
Checklist
I have read the contributing guide
My changes follow the style and formatting of the project
I have commented in any hard-to-understand areas (if needed)
I have reviewed the site locally and ensured no new warnings appear
No documentation changes were needed for this update
This PR does not introduce any functional regressions